Back to Main Menu

MapInfo Professional: Level 4 Integration (Database Triggers) Workflow

Background

To facilitate Level 4 Integration between myData and MapInfo, a series of database triggers are applied to both databases to support the following functions:

• Adding new assets in MapInfo, creating these assets in myData, returning the next sequential Asset ID to the objects created in MapInfo.
• Tagging deletions made in myData in a field in the MapInfo database.
• Tagging deletions made in MapInfo in a field in myData.

Level 4 Integration is typically only configured on asset categories whose assets always originate in the GIS.

 

Exceptions can be made for assets created in myData as a result of using the Asset Split tool (please check with Assetic to ensure that this function is enabled).

myData Configuration

To support Level 4 GIS Integration using Database Triggers, linked asset categories in myData must have their Asset ID Mode set to Auto Generated.

 

Assetic also recommends switching off the ability to Create assets in myData to ensure that all assets originate from the GIS.

 

To verify these settings, please check the configuration in Tools > Category Configurations.

Adding New Assets

To add a new asset, simply draw the object in MapInfo as you normally would.

 

You may draw multiple assets in any one edit session.

 

The database triggers do not get activated until you save the changes in MapInfo.

 

Once you are happy with your new assets, hit the Save button.

IDs will get generated automatically once you save your changes.

 

Once objects are saved in MapInfo, they will be created in myData and the next sequential Asset ID(s) will be assigned to the newly created objects in MapInfo.

 

Please note that you may need to hit the Refresh DBMS Table button in MapInfo  to see the New Asset IDs, and the Refresh Navigation Panel button in myData  to see the new assets.

Deleting Assets in MapInfo

Delete assets in MapInfo as you normally would. Any assets that have been deleted in MapInfo will be tagged as ‘Deleted by GIS’ in the myData field nominated to tag this information.

 

MyData users can easily search for assets deleted in MapInfo and then choose to follow the correct myData disposal procedure to ensure that valuation data is accounted for.

Deleting Assets in myData

Permanently delete or dispose of assets in myData as you normally would.

 

Any assets that have been deleted in myData will be tagged with a ‘1’ in the MapInfo field nominated to tag this information.

 

MapInfo users can easily search for assets deleted in myData and then choose to also delete them from the GIS.

Using the Split Tool in myData

If exceptions for the Split Tool have been enabled for myData, you may use this to assign correct valuation data to assets, however, you will need to manually assign the new Asset IDs to objects in MapInfo.

 

Use the Split Tool in myData as you normally would – this will dispose of the original asset, and create a number of new assets to replace the original with new Asset IDs automatically generated.

 

In MapInfo, draw the split assets in as new objects.

 

Before saving your changes, manually assign the Asset IDs generated by the Split Tool in myData to the objects you have just created.

 

Click 'Save' once complete, taking care to ensure that Asset IDs have been copied across accurately from myData.

 

You will notice that the original asset has been tagged as deleted in myData.

 

Feel free to delete this asset from MapInfo once the new assets have been created.

Using the Merge Tool in myData

Use the Merge Tool in myData as you normally would – this will keep one nominated asset as the parent and dispose of the others.

 

In MapInfo, edit the parent asset so that it replaces all assets included as part of the merge.

 

You will notice that the other assets have been tagged as deleted in myData.

 

Feel free to delete these assets from MapInfo once the parent asset has been adjusted.